This week was a little slower since our team has been waiting for parts, which I put in orders for on Wednesday. So far we have received our OBDII to VGA cable in the mail via Amazon, and I was able to find my OBDII port on my own car for testing. The wire is long enough for our device to fit on the dash. We also decided to pivot from our camera idea since it didn’t have enough value for the end consumer. I also solidified which data I was using from the OBDII port so I can target specific sections of the CANBus data string, and came up with a data schema for my part of the project for our final design presentation. I researched more about the makeup of the OBDII string and where the specific data is located, and made some bit shifting masks that we will be using on our Raspberry Pi to find velocity, accelerator position, hazard lights and steering wheel information.
Team Status Report 3/6/2021
This past week we solidified the overall structure and flow of our data pipeline. We plan on having two processes running on the RaspberryPi at the same time. One process will be continuously receiving, filtering, and decoding the CANbus data and writing it into a local SQL database. The other process will be reading and analyzing each new entry from that local database. After processing the data, we decided that the second process will send it to the AWS IoT console via MQTT protocol. Lastly, the web application will read all the data written to the AWS console and visualize it with charts and graphs. We also discussed how we are going to integrate the different software components. We decided on the format that the data would be in so that we could build our separate pieces of software knowing how the data will look when it is received. Lastly, we decided on the specific pieces of information we would need from the CANbus in order to perform a quality analysis of a person’s driving.