Nate - Senior Hardware designer at Nuvation, PM for MSX
- Has used Elcon chargers before
- MSX used the SMC100s as a backup motor, they had it working.
- TI has support engineers, for reference boards, etc - SDC contacts - TI reps are assigned geographically.
Present: Aashmika, Micah Bai, Arshan, Josh, Micah Black, James, Jenny, Chen, Lauren, Jessica, Darby
Aashmika went through general car overview of the electrical system
MSX BMS:
Go/No Go for battery parameters
ADI8280 over SPI for voltage/temperature
MSIX used a purely logic system for the BMS
Scrutineering just needs to see contactors open for 3 conditions
Steering
Critical buttons should not be on screens, they should all be physical buttons
Tablets for a screen, Pi creates a wireless connection that the tablets connect to. You have a whole app ecosystem to use. Kiosk (lock down the tablets) app that would navigate to a webserver hosted on the Pi. With the webserver, we can connect to it with our laptops when debugging the car as well. Just let the tablet run a native android OS. Open ports for specific devices to access.
Double sided foam tape on the tablet, attach it from the back side of the opening, and it looks like you are not really using a tablet.
For telemetry - wireless CAN bridge over the 400MHz? band - is transparent to the network - cream colored project boxes should be somewhere.
MSX used 3 different CAN buses - TI part that had 3 CAN buses, and aggregate the data.
-Telemetry
-Battery
-Control
Strategy timesaving - should be able to drive without the Pis booting up - get away from pitstops quick.
Short distance wireless communications should work well within the car.
The steering wheel gets abused the most. Make the steering board robust. Discrete buttons with the fly-wire to the board. Prevent the button from being over-pressed.
Power Distribution
LTC4417 Power Path Priority
A lot going on in this board.
For previous versions there was CAN and power over the same wire, so some questions about the CAN hub.
RGBW serial lights that can go different colors. MSX used the flash LEDs from blackberry. Kapton tape for the Amber lights.
Motor Controller
MSXII Precharge was hardware based.
Conformal coatings
Silicones based conformal coating comes up as a strip - toluene can caused hearing issues - use a fume hood.
Bi-Metal strips for the thermostats - can be used as an upper bound for voltage monitoring.
Available in 5 degree increments
Lights Boards
Thermal Vias - Usually spaced as close as possible, and as small as possible.
Heatsinking to something must be able to radiate the heat as well.
Aux Charger
Rules used to be primary cell Aux.
If someone wants to take this on, then this is a great project to do.
Keep one-upping the scrutineers for regulations
Solar Sense
What is the issue?
Yellow construction work lights for testing the panels
Spool of wire for loads,
Raceware Tech - MPPTs that were programmed for settings.
Robustness - They'll fail and the no one will no how to fix them.
DC-DC Modules
Vicor modules have the switching logic inside, but the components outside.
Solving the heating problem - bigger package - larger heatsink - bigger fan.
Thermistor switch for controlling the fan.
Management Input Perspective
Break in to teams to work on projects - mentor relationship
If not working on the board, probably not ideal to bring up the board - usually ends up in more broken boards.
Battery
MSX did battery testing - capacity - great job for co-ops
Why did this knowledge not get transferred to MSXIV
Lithium at low voltage is not dangerous??
Firmware
See Arshan's firmware overview presentation
Measuring MPPT currents - measure battery current, measure load - Solar is the difference
Undervoltage fault - current directional fault - disable fault while charging
Killswitch - Regening on to a bus, but you lose the load - voltage spike - the killswitch should be wired through the motoro controller relays as well.
BPS Strobe - Through the power distribution rear board
How do we check our battery states - can we see them when powered on the AUX?
Have a timer on the current direction (30 seconds) - prevent misuse (driving it beyond low)
Driver is not going to interact with the Idle state
Write a user manual
Nate knows about the relay hysteresis issues - seems like a common problem.
DC-DC Overtemp
In any states, the fault goes to an emergency - take action based on where you came from.
If you aren't able to close the contactor - there is no reason to do precharge - do we still want firmware control?
Time sequence delay for heartbeats - make sure its within the acceptable range.
MSX was taken to FSGP 9 with code that Nate wrote ("scary because I'm not a coder")
-Arshan should be thinking about the state diagrams, etc, CAN communications, GPIO driver, CUBE implementation, etc
-Code written by others should work at a black box level to what a lead defines.
-Start at the high level, eat the dots going to the lower levels
-Complete your task before I do.
-Do the architecture RIGHT. Give yourself the time for this. If this is wrong, then any code written will also be WRONG.
-CAN Message Maps
-State transitions, etc
-What to do when in a state if you don't want to be there
-Do you need state __?
-High level testing can be done on Linux, mock out the drivers, etc. HIL testing - make sure it is working on a controller board as well - use a Pi to provide any inputs necessary.
-Backend database for logs on the Pis
-Lift the wheels off the ground and do all the remote control testing
-Interior mirrors that go out through the windows
Anything that people will be interacting with should be designed for robustness.
MSX had issues with brake testing.