Design:
- One FSM for power management
- One FSM per each power transition (off → on, off→ battery)
To-do:
- Don't know how the precharge method happens in terms of the car:
- ask Micah Black
- Look up MS12
- ask the ms12 people
- Need to bring in charging into the equation.
- Add a watchdog timer for precharge.
CAN Messages:
Destination | Purpose | Message ID |
---|---|---|
Front Power Distribution | Turn on Driver Display during power on (to possibly show error messages) | |
Rear Power Distribution | Turn on BMS Carrier | |
Get Aux Status | Simple message, acked with OK if the aux battery level is enough. | |
Get DCDC Status | Simple message, acked with OK if DCDC has switched. | |
Begin Pre-Charge | How do we pre-charge? for now, assuming a simple message with ack. | |
Meeting 1 notes:
Discussed:
- CAN interface between boards
- Exclusive CAN Networks (Main Car System, Charging, motor control)
- Connections between different
Questions/Concerns:
- What boards will CC connect to
- What boards always powered on
- Does the brake have to be pressed to turn on the car?
- Lights inside PRND buttons to turn on when pressed?
- Hazard lights work when car is off?
Next Steps:
- Research CAN interfacing
- Read buttons from board
- Learn Interrupts
- Talk to Hardware, generate list of what boards will be interfacing with the CC
Deadlines:
- TBD
Centre Console Info
Centre Console Components:
Read Buttons:
- Power
- Park
- Reverse
- Drive
- Neutral
BPS Fault:
- LED indicator
Hazards:
General flow of console:
- Central console is always on to listen for power button
- Will turn on if pressed,
- Press button
- Controller board sends signal through CAN
- Power distribution board detects signal
- Power distribution board makes necessary checks and acts accordingly
- Controller board does other stuff