This week I worked more on the website which we will be using to display the real time notifications and user driving report. A lot of my work this week was done on planning out the exact process I will go about on working on this piece of the project and how to integrate it easily with my other team member’s parts, which involved a group effort of ironing out the design our overall system. We decided we will be using AWS as our database, since we can send the driving data to AWS via MQTT and also access this data from the website. Once the data is sent from the Raspberry Pi and received on the server, I can take the data and write Javascript code to interpret the data into different charts and lists to display on the website. For example, on the driving report page, we plan to have a complete summary of the user’s drive, split up into parts such as: a chart of their speed, amount of time and distance driven, list of infractions, chart of efficiency overtime, etc. Aside from planning, I also continued work on the actual development of the website and created the HTML and CSS for two static pages with the basic template of the final website. The infractions page is just a simple box on the screen where the text will update/flash when an infraction is detected from the server. The other page is the driving report page, and has the layout for where we will be placing the data also when it is received from the server. Apart from the website, I also spent time doing research on OBD-II data formatting and how exactly we can read this data. I found that the the data has a standardized format array of bytes where each block of the data represents some piece of the information, which is logged online. We simply can create a bit mask based on the data we need and extract it.
Next week, I plan to setup the website with AWS now that I have received credits so that we can host the website and start storing/retrieving data and be ready for when we get the ODB-II reader going.