| Page Properties | |||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Document status | Status | title | DRAFT
Developers | QA | Karl Ding
|
Goals
- Wirelessly relay vehicle telemetry data sent on the CAN bus to the laptop device in the chase vehicle
- Provide GPS positional data via a GPS receiver (that the microcontroller communicates with over either UART or SPI)
- Design a user interface that is useful, aesthetically pleasing, maintainable, and intuitive to use
- useful: provides an overview of the important data at a glance; presents all the necessary information in a detailed format if necessary
- aesthetically pleasing: looks good, fits the context
- maintainable: something that can be iterated upon without the new maintainer wanting to kill themselves
- intuitive to use: user experience flows well, careful thought put into various use cases
- It should "just work"
...
| Question | Outcome |
|---|---|
| How much space do we need to store the CAN data? | |
| Are we planning on implementing a new protocol on top of the CAN bus? | Yes. The motor controllers will have their own network, and "our" CAN network will communicate with the motor controllers via an intermediate board that "translates" messages to the motor controller manufactor's specifications. See CAN Message Protocol for more information. |
| Filesystem vs treating the SD card as a binary blob? |