...
| Page Properties | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Note
The hardware component of the driver display is handled by a Raspberry Pi 3B+ which is mounted to and powered by the Center Console board directly. The pi currently uses a PCAN dongle for getting information from System CAN, but can be changed to use Ethernet and the Tritium CAN-Ethernet bridge with minimal effort.
Goals
We want to design a vehicle dashboard that acts as an instrument panel to the driver
The dashboard design should provide the pertinent information at a glance
...
- This will be displayed on a LCD display mounted on the vehicle, which will be visible to the driver.
Requirements
The driver display should show the following
| # | Title | Notes |
|---|---|---|
| 1 | Speed | How fast the car is moving |
| 2 | State of car | Drive/Park/Reverse |
| 3 | Power Usage Percentage and Charge | A bar that scales based on how much of your peak power you're using If you're using regen, and how much you're generating |
| 4 | Fault Information | Communicate errors to the user |
| 5 | Turn Signals/Hazards | Indicators for turn signals |
| 6 | "Car is Ready to Drive" | Some indicator that the car is ready to drive |
Design
It is our belief that as an electric vehicle, we should showcase and design to accentuate the strengths that an electric vehicle has. This is not to say that we want to present a completely novel user-experience that throws away any preconceptions of how a vehicle should run—rather, we wish to build upon preconceived notions of a "normal" car, and adjust certain areas of the User Experience to better match with the user's expectations. For the majority of of our drivers, they have not driven in an electric vehicle, and the goal is to present an experience such that we can take "anyone off the street, put them in our car, and they can drive it." This means our interface should remain familiar to the driver, and retain design hinting or provide hints.
...