We wrote our initial proposal presentation and presented on Monday. This week, we debated our final design after reading our presentation feedback. We discussed more about how we plan to interpret the data and also found studies done online which look into different ways to interpret this kind of data for driving infractions. Our team solidified our parts list which we will be sending out on TAs before class on Monday. In terms of design, we decided to stick with the PiCan port and add a GPS to our system to track the user’s location and correlate it with Google Maps API data. We updated our GANTT chart to account for delays in the ordering process. For software, we requested AWS credits to help run our website on the backend and set up our Google Maps API and received an API token we can use for the rest of the project. Next week, we plan to make more progress on our individual tasks. This entails, having a working webpage, and starting to setup the Raspberry Pi for receiving and sending data from the OBD-II after our parts are received.
Samraj’s Status Report for 2/27/21
This week I worked on setting up the web application where we will be displaying out infraction warnings in real time as well as the final driving report. I started with setting up the overall layout of the website, using a Bootstrap template. I also researched into how we plan to send data from the Raspberry Pi to a database so that the website is synchronized. For this, I plan to use the AWS iOT core which will allow me to send data from the Raspberry Pi to AWS via MQTT over a mobile hotspot we will use in the car. The website can then read this data and update the warnings and prepare the report as needed. In preparation for next week, I also researched how to dynamically update data on a website from AWS so that we can continually read and update the screen. All of our code will be shared through Github, so I setup a shared repository where all of the website code will be pushed. Next week, I plan to continue on the website by making it so that I can receive AWS data on the website and update the page. Ryan will work concurrently on getting the Raspberry Pi to send the data so that we will be able to both send and receive sooner.
Samraj’s Status Report for 2/20/21
This week, we shifted our project idea from a smart heating system to this smart driving instructor. Most of my work this week was done in helping my team come up with this new idea and research it’s feasibility. Since our project relies on communicating data from the OBD-II port to the Raspberry Pi, I did some research into the tools we need to achieve this and found that we need to order a PiCAN2 CAN-Bus Board, along with a Raspberry Pi, and an OBD-II cable. I also started to setup the website that we will be using in our project in order to display and store the data by setting up a host and a basic page. We seem to be on track for next week where we will start to get the project fully rolling and hope to order parts and continue with the website.
Ryan’s Status Report for 2/20/21
This week we spoke with our professor and TA about the shortcomings of our initial idea. Since our meeting on Monday, I spent time considering other ideas for our capstone project. When we decided on a driving assistant I spent time researching the different ways of tracking car data. We discussed bringing in our own sensors that would attach to a RaspberryPi, but came to the conclusion that in order to get the widest range and most accurate data measurements, the best option would be to gather the information from the CANbus through the OBDII port. I researched a few methods for getting this data including commercial solutions that came with their own software, but decided that with a RaspberryPi and PiCAN attachment, we could collect and decipher the CANbus data ourselves. Additionally, I contributed to the proposal presentation slides we made.