Lights Control: MS 12
- Kevin Chen (Unlicensed)
- Arshan Khanifar
- Titus Chow
- Veronica KH Lee (Deactivated)
Owned by Kevin Chen (Unlicensed)
Goals
- Efficient control of the on/off state and brightness of each light
Background and strategic fit
MSXi used a single lights board for the entire car. It was controlled by driver controls over CAN, which worked relatively well.
Our current plan is to design our new lights board to be used in both the front and back. It would then use the wiring harness to determine which CAN messages to react to.
Requirements
| # | Title | User Story | Importance | Notes |
|---|---|---|---|---|
| 1 | Handle turn signals/braking/hazard lights | We need to be able to support any order of signals without breaking. | ||
| 2 | Handle horn | We plan on using the lights board to drive the horn. | ||
| 3 | Handle strobe | We plan on using the lights board to flash the strobe light. | ||
| 4 | Support Tesla headlights | We plan on using Tesla headlights, so we need to be able to drive them. | ||
| 5 | Control Reverse Lights | The car needs to turn on its reverse lights when reversing. | Not sure? |
Questions
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|---|
| How do we handle critical vs. non-critical lights? | The only critical light is the strobe light, so the rear will be powered by the critical rail and the front will be non-critical. This keeps the horn from ever drawing from the supplemental battery. |
| Don't we need reverse lights? |