Description | BMS Carrier Firmware |
---|---|
Target release | MSXIV |
Epic | |
Document owner | |
Project leads | |
Team members | Arshan Khanifar Zubair Waheed (Deactivated) |
Goals
<put summary of project here>
Background and strategic fit
CAN Communication
Requirements
Meeting Notes
- logs all
- Voltage,
- Temp,
- Current
- Relay States
- Controls
- Relays
- used for state of the charge model:
- state of the charge status of battery how much eneergy
- we need fast logging for a good soc model
- overcharge
- over temperature
- over current
- undercharge
- power distribution tells u something’s wrong
- dc dc failed
- precharge board:
- precharge failed
- controls the relay
- if AFE undervoltage, we disconnect the entire relay
- you can also disconnect from car power button so that comes from can
- other conditions:
- controls fans based on the temp
- car turn on: checks battery pack status, then connects relays
- turns on the current sense board: firmware doesn't need to care it's literally a line that goes to it.
- PI will be SOC algorithm
- connetion between pi's havne't made decision
How it works:
- Three AFE's
- gpio's control the mux
- adc: for reading measurements
- we talk to this bish using iso-spi
- LTC6811 is the chiB
Questions
Question | Answer |
---|---|
What are the conditions under which we disconnect the relays? | |
How many ways are there to change the relay state? Is BMS Carrier the only one controlling them? | |
What are the incoming CAN messages? | |
What are the outgoing CAN messages? | |
How is state of charge calculated? | |
What's the maximum rate we can have for voltage measurement? | |
What's the maximum rate we can have for current measurement? | |
What should it do when we power the car ON? | |
How are we computing the SOC? |