Project
# | Title | Team Members | TA | Documents | Sponsor |
---|---|---|---|---|---|
10 | Automotive Data Logger |
Jacob Drewniak Michael Jang |
Evan Widloski | design_document0.docx design_document0.pdf final_paper0.docx presentation0.pptx presentation0.pdf proposal0.docx |
|
Web Board Link: https://courses.engr.illinois.edu/ece445/pace/view-topic.asp?id=27132 Members: Michael Jang (myjang2) Jacob Drewniak (jdrewni2) # Problem * The Illini Motorsports team builds a Formula style car from the ground up. Verifying the initial design requires significant data collection from numerous testing sessions. Unfortunately, most existing data logging solutions are quite expensive and have slow data download rates. Additionally, the Vector CANtech data logger we have used in the past uses proprietary software that is unintuitive and difficult to use. # Solution Overview * Our solution will be cheaper and much more intuitive to use than anything store-bought. We plan to design and implement a PCB that takes sensor data that has been sent over CAN (automotive specific communications protocol) by our team’s sensor processing module and sores it in non-volatile memory. We will then make this data available to the user through USB and Bluetooth connectivity. We will also include a connector to use a Particle Electron daughter board that we’ve used in the past to upload incoming data to a custom website over 3G. # Solution Components ## Sensor Subsystem * This board will be required to log data from a wide variety of sensors ranging from strain gauges to thermocouples to pressure sensors in order to verify design decisions made by other members of the team. Because we already have a fully functional sensor processor design from previous years that handles all this data and converts it into CAN messages, the only sensor included on the board will be a simple temperature sensor for diagnostics purposes. ## Processing Subsystem * There will be some form of non-volatile memory (NVM) to store incoming data. There will also be a UART to USB IC and a Bluetooth IC to communicate using these protocols. We will include a PIC32MZ microcontroller for CAN message reception and conversion, supercapacitor pack control, and data transfer from NVM to USB and Bluetooth. Because the microcontroller can’t read CAN directly, there will be a CAN transceiver IC included as well. ## Power Subsystem * Two regulators will be need for 3.3V and 5V. The 5V will originate from our car battery (13.5V), and the 3.3V will come from the 5V. These regulators will power modules such as CAN transceiver/termination, data interfaces, and microcontroller. The car battery will also directly power our supercapacitors and the backup controller (Linear Technology LTC3350). The backup controller will monitor and regulate the current, voltage, and charge of the supercapacitors. This system is needed in the case that the car suddenly loses power. The capacitors will continue to power the PCB so that no data is lost. # Criterion for Success * A successful implementation will be able to collect all sensor data throughout the car, and display the data onto a device through USB, Bluetooth, and 3G. The design should also be able to successfully save data from the supercapacitors in the case that the power to the car is lost. |